Internet Archive's in-browser bookreader "theater" requires JavaScript to be enabled. It appears your browser does not have it turned on. Please see your browser settings for this feature.

Net Yaroze Documents

by: Sony Computer Entertainment Europe

Publication date: 1996-12-01
Topics: Sony Computer Entertainment Europe, SCEE, Net Yaroze, documentation
Collection: playstationmanuals; consolemanuals; manuals
Item Size: 275.4M

Sony Computer Entertainment Europe

Net Yaroze - Documents

010-1997-startupguide (f_start.pdf g_start.pdf)

Start-Up Guide - An introductory booklet explaining the contents and requirements of the Net Yaroze Starter Kit.

It gives step-by-step instructions on setting up the Net Yaroze software on your PC. And also explains how to run software on the Net Yaroze system.

020-1997-userguide
User’s Guide - A reference manual explaining how to create software for the Net Yaroze system.

030-1997-libraryref
Library Reference - A manual listing and describing the functions and structures in the Net Yaroze libraries.

040-1997-fileformat

Explains the popular Net Yaroze formats (Little-Endian, structs read from left (Lease Significant Bit end) to right (Most Significant Bit)).

The 1996_ files where included on the Net Yaroze - PC CDROM , and can be ignored.

050-1998-tod1 & 060-1999-tod_tutorial-jasons07

In Aug 1998 SCEE added the TOD plugin and example, member jasons07 later created this tutorial on how to use it.

Plugin available here: https://archive.org/details/webyaroze.7z

VDF (MIMe) was undocumented (and no plugin provided) but the T-Rex Dino example was available to study.

From the newsgroups:

Subject: Re: TOD vs VDF files...?
Date: Fri, 14 May 1999 17:27:28 -0500
From: Nathan Miller
Newsgroups: scea.yaroze.programming.3d_graphics

>What are the advantages of a .TOD file versus a MIMe file?

A TOD format file is the best format to use if you are making some sort of
in-game cut scene like you see in Metal Gear Solid. It allows you to
manipulate cameras, lights and models using time as a measurement. It could
also be used to make things appear out of nowhere and other special effects.

>Does it stand to reason then that gteMIMefunc is faster than the .TOD
example because the .TOD example does all the manipulation by hand?

Yes, it is going to be faster because it uses the GTE to transform all of
the vertecies. This is the method that you would use if you are doing some
internal animation, or animation of a 3d object not relative to the world
around it (like walking or whatever). It works with model data only,
vertices etc., and not with light location or camera location (or even
model location for that matter!)

>If .VDF is considerably faster, then it may be the better choice. Is
>there a .TOD->.VDF conversion program?

Using the above two explanations as a guideline, determine which is best for
you to use. I do not think that there is a conversion program due to the
fact that they deal with two very different types of 3d animation.

>If not, does someone have the
>.VDF specification that I may write one?
>

I think that VDF stands for Vertex Differential File and was made
specifically for that project (I am speculating). But the idea behind it is
very simple because a VDF file uses GteMIME just like you will have to!
Basically, all you are doing is giving your model a list of vertex position
changes that are handled through the GteMIME function. These changes are
divided into frames and you can keep track of which frame you are on and how
long it will take to change frames.
BUT TO MAKE EVERYTHING SIMPLE, I RECOMMEND GOING TO THE SCEE SITE AND
GETTING CRAIG GARAHAM'S RSDANIM V1.6. IT OUTPUTS A MIME FILE AND IS VERY
EASY TO USE!!

>Thanks again.
>
>Steven

Well, I hope that helped a little.

Nathan Miller